docs(workflows): guard the security caller template against Dependabot startup_failure#33
Conversation
…t startup_failure
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Review limit reached
Next review available in: 43 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Fix the caller template at the source
The documented
security-scan.ymlcaller template (and thesecrets: inheritnote) is what every repo copies itssecurity.ymlfrom. As written, itstartup_failures on Dependabot PRs: GitHub doesn't grant secrets to Dependabot-triggered runs, and a cross-repo reusable-workflow call withsecrets: inheritcan't start in that restricted context → the required check never passes → Dependabot's own security-fix PRs are blocked from merging.This updates the template to include the guard and documents the caveat, so new repos inherit the fix:
Dependabot already vetted the bump;
push/scheduleruns still scan the default branch, so coverage is unchanged.Complements the per-repo rollout of the same guard (crates#120, viz#122, pypi#67, vcpkg#24, docs#88, dev#29, npm#137, programs#43, dotnet-sdk#73). Docs-only change — no active workflow is modified here.